<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright 2008-2011 Andreas Huber Doenni. Distributed under the Microsoft Public License (Ms-PL).
See accompanying file License.txt or copy at http://mews.codeplex.com/license.
-->
<Message>
    <Header>
        <UnstructuredHeaderField name="MIME-Version">1.0</UnstructuredHeaderField>
        <ParameterizedHeaderField name="Content-Type" value="multipart/mixed">
            <Parameter name="boundary">----- =_aaaaaaaaaa0</Parameter>
        </ParameterizedHeaderField>
    </Header>
    <MultipartBody subtype="mixed">
        <Preamble />
        <BodyPart>
            <Header>
                <ParameterizedHeaderField name="Content-Type" value="multipart/mixed">
                    <Parameter name="boundary">----- =_aaaaaaaaaa1</Parameter>
                </ParameterizedHeaderField>
                <UnstructuredHeaderField name="Content-ID">&lt;20592.1022586929.1@example.com&gt;</UnstructuredHeaderField>
            </Header>
            <MultipartBody subtype="mixed">
                <Preamble />
                <BodyPart>
                    <Header>
                        <ParameterizedHeaderField name="Content-Type" value="multipart/alternative">
                            <!--
                            The value of the boundary parameter given for this nested multipart is the *same* as the one
                            of the outer boundary. Firstly, according to RFC 2046 5.1.1. (see first paragraph on page
                            22) this is clearly illegal. Secondly, according to RFC 2046 5.1.2. the outer boundary must
                            always take precedence over the inner boundary. In this case they are indistinguishable, so
                            any boundary occurrence must be interpreted as being an outer boundary.
                            -->
                            <Parameter name="boundary">----- =_aaaaaaaaaa1</Parameter>
                        </ParameterizedHeaderField>
                        <UnstructuredHeaderField name="Content-ID">&lt;20592.1022586929.2@example.com&gt;</UnstructuredHeaderField>
                    </Header>
                    <!--
                    No body appears because this multipart body is cut short by the appearance of a delimiter
                    of an outer multipart
                    -->
                </BodyPart>
                <BodyPart>
                    <Header>
                        <ParameterizedHeaderField name="Content-Type" value="application/octet-stream" />
                        <UnstructuredHeaderField name="Content-ID">&lt;20592.1022586929.3@example.com&gt;</UnstructuredHeaderField>
                        <UnstructuredHeaderField name="Content-Description">patch1</UnstructuredHeaderField>
                        <ParameterizedHeaderField name="Content-Transfer-Encoding" value="base64" />
                    </Header>
                    <ApplicationBody subtype="octet-stream">XXU=</ApplicationBody>
                </BodyPart>
                <BodyPart>
                    <Header>
                        <ParameterizedHeaderField name="Content-Type" value="application/octet-stream" />
                        <UnstructuredHeaderField name="Content-ID">&lt;20592.1022586929.4@example.com&gt;</UnstructuredHeaderField>
                        <UnstructuredHeaderField name="Content-Description">patch2</UnstructuredHeaderField>
                        <ParameterizedHeaderField name="Content-Transfer-Encoding" value="base64" />
                    </Header>
                    <ApplicationBody subtype="octet-stream">XXU=</ApplicationBody>
                </BodyPart>
                <!--
                The above body part was terminated by the appearance of a close delimiter, so everything that follows
                must be interpreted as epilogue.
                -->
                <Epilogue>
------- =_aaaaaaaaaa1
Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa1"
Content-ID: &lt;20592.1022586929.6@example.com&gt;

------- =_aaaaaaaaaa1
Content-Type: application/octet-stream
Content-ID: &lt;20592.1022586929.7@example.com&gt;
Content-Description: patch3
Content-Transfer-Encoding: base64

XXX

------- =_aaaaaaaaaa1
Content-Type: application/octet-stream
Content-ID: &lt;20592.1022586929.8@example.com&gt;
Content-Description: patch4
Content-Transfer-Encoding: base64

XXX

------- =_aaaaaaaaaa1--

------- =_aaaaaaaaaa1
Content-Type: multipart/alternative; boundary="----- =_aaaaaaaaaa1"
Content-ID: &lt;20592.1022586929.10@example.com&gt;

------- =_aaaaaaaaaa1
Content-Type: application/octet-stream
Content-ID: &lt;20592.1022586929.11@example.com&gt;
Content-Description: patch5
Content-Transfer-Encoding: base64

XXX

------- =_aaaaaaaaaa1
Content-Type: application/octet-stream
Content-ID: &lt;20592.1022586929.12@example.com&gt;
Content-Description: patch6
Content-Transfer-Encoding: base64

XXX

------- =_aaaaaaaaaa1--

------- =_aaaaaaaaaa1--
</Epilogue>
            </MultipartBody>
        </BodyPart>
        <BodyPart>
            <Header>
                <ParameterizedHeaderField name="Content-Type" value="text/plain">
                    <Parameter name="charset">us-ascii</Parameter>
                </ParameterizedHeaderField>
                <UnstructuredHeaderField name="Content-ID">&lt;20592.1022586929.15@example.com&gt;</UnstructuredHeaderField>
            </Header>
            <TextBody subtype="plain" format="Fixed">--
It's never too late to have a happy childhood.
</TextBody>
        </BodyPart>
        <Epilogue />
    </MultipartBody>
</Message>